Copyright: Copyright ¸ 1986,1999 Danware Data A/S
Citation: NetOp® and the red kite are registered trademarks of Danware Data A/S.


Welcome to NetOp Remote Control Version 6.5

Welcome to NetOp Remote Control, a Danware Data product for remote control of PCs over a wide variety of communication standards. Select one of the following options

Quick Guide

User interface overview

Configuration

Program Options

   Communication Profiles

Security

Gateway security

The Log Setup

Chat

Request Help

Remote Printing

Online Support

For Administrators on Windows NT and Windows 2000

Copyright © 1986,2000 Danware Data A/S. All Rights Reserved. Portions used under license from third parties. NetOp® and the red kite are registered trademarks of Danware Data A/S. Windows (TM) is a trademark of Microsoft Corporation.


User interface overview

Title bar

In the Toolbar, which is placed below the menu bar, shortcut buttons for the most common commands are available.

Menu bar

Tool bar

Status line

The status line at the bottom of the NetOp Host window contains menu hints, which show a brief description of the menu entry currently selected.

Host ID

In this field the name of the Host is entered. This is the name that Guests will use to identify the Host.

Communication profile

This is where the communication profiles are selected. Each communication profile is based on a communication device, and has parameters specific to that device.


Menu Bar

File

Exit

Connection

Wait for call

Stop Host

Hangup

Utilities

Chat

Request Help

Cancel Help Request

File transfer status

Modem Dialog

Configuration

Program Options

Guest Access Security

Gateway Access Privileges

Maintenance Password

Log Setup

Communication Profiles

Modem Database

Access Server Setup

Help

Contents

Using Help

About


File Menu - Exit

Select this options to exit the Host program


Connection Menu - Wait for call

Select this option to have the NetOp Host Wait for Call.


Connection Menu - Stop Host

Select this option to stop the Host.


Connection Menu - Hangup
Connection Menu – Hang up

Select this option to hang up from the currently connected Guest.


Utilities Menu - Chat

Select this option to Chat with a Guest.


Utilities Menu - Request Help

Select this option to Request Help from a NetOp Help Provider.


Utilities Menu - Cancel Help Request

Select this option to cancel a Help Request .


Utilities Menu - File Transfer Status

Select this option to view the status of a current file transfer operation.


Utilities Menu - Modem Dialog

Select this option to view the Modem Dialog .


Configuration Menu - Program Options

Select this option to view the Host's Program Options .


Configuration Menu - Guest Access Security

Select this option to configure Guest security.


Configuration Menu - Gateway Access Security

Select this option to configure Gateway Security.

 (Note this option is only available on a NetOp Gateway).


Configuration Menu - Maintenance Password

Select this option to configure the Host's maintenance password .


Configuration Menu - Log Setup

Select this option to specify log settings .


Configuration Menu - Communication Profiles

Select this option to view and maintain the Communication Profiles database.


Configuration Menu - Modem Database

Select this option to view and maintain NetOp's Modem Database .


Configutation Menu - Access Server Setup
Configuration Menu - Access Server Setup

Select this option to either enable or disable the NetOp Access Server.


Help Menu - Contents

Select this option to view this Online Help System.


Help Menu - Using Help

Select this option for a quick guide on how to use this Online Help System.


Help Menu - About

Select this option to view information About the NetOp Host.


Program Options

Select Program options from the Configuration menu to configure various Host options. This dialog is set in tabbed format containing six sections:

General

Host Name

Connection Notification

Audio

Remote Printing

Help Request


Program Options - General

Wait for call at program startup

If this option is enabled, the Host will not wait for the user to enter configuration information when started but rather initialize with the information, which was used the last time the Host was run.

Load Host at Windows startup

When this option is enabled the Host will automatically load when Windows starts. This option is normally used in conjunction with Wait for call at program startup and Minimize Host at program startup.

This option intelligently handles differences between Windows/Windows for Workgroups 3.1x, Windows 95, Windows 98, Windows NT and Windows 2000:

Windows/Windows for Workgroups: The Host is loaded via the RUN= line in the WIN.INI file.

Windows 95/98: The Host is loaded via the registry.

Windows NT/2000: A special 32-bit NetOp Host service is added.

This option will enable you to remote control the login screen of Windows 98/95 and NT/2000 PCs

Minimize Host at program startup

Enable this option to run the Host minimized. This setting is useful when the Host is loaded automatically.

Stealth mode (hide Host when started)

This option allows the Host user to hide the Host program from view. The Host program remains invisible until a special program called SHOWHOST is run. The "SHOWHOST.EXE" program is found in the NetOp directory and can be renamed or copied to another location such as a diskette. This option takes effect when you restart the Host program.

Minimize program on connection with Guest

When this option is enabled, the Host will minimize whenever a Guest connects to it.

Let the Host always be the top most window

When this option is enabled and the Host is being controlled, the Host window will always be on top (both as a window, and when minimized to an icon on Windows 3.x and NT 3.x). This makes it easier to know when a remote control session is active.

Show file transfer status

This option allows the Host user to monitor a file transfer when initiated by the Guest.

Send Keep Alive message

NetOp uses a non-polling communication technique. In a sense this means that if there is nothing to be sent between Guest and Host (e.g. keystrokes from Guest to Host or screen changes from Host to Guest) nothing will be sent. By checking this options you will be sure that a connection timeout will occur if there is a bad or unstable connection between the Guest and Host. This option should be unchecked if you where to take advantage of the CAPI short-hold-mode feature or if communicating through e.g. an ISDN router that should be shut down if there is no activity to save cost.

Restart Windows after hang up

This option shuts down and restarts Windows after hang up. The shutdown is "unconditional", which means that open programs will be closed even if they contain unsaved information or documents.

Log off Windows after hang up

On Windows NT/2000/95/98 you also have the possibility to log off Windows after hang up. If you have checked this option, NetOp will log you out of the computer when the connection is ended. If you also have checked "Wait for call at program startup" and "Load Host at Windows startup" another Guest can connect to the machine but gets the "Press Ctrl + Alt + Delete to log on" prompt on Windows NT/2000 or the Windows 95/98 login dialogs.


Program Options - Host Name

Enter name or leave blank

Enable this option if you wish to enter your own name in the Host ID field or if you wish to leave the Host ID field empty.

If you leave the Host ID field empty, NetOp will use the machines MAC address if IPX or NetBIOS is enabled. If an IP-based profile is used, then NetOp will use the machine's IP address as the Host ID.

If a NetOp Gateway is being used and IPX, NetBIOS and TCP/IP (UDP) are being used, NetOp will use the IP address as a way of identifying the Host on a browse list.

Use environment variable

Enable this option if you wish to use the value of an environment variable as the Host name. When this option is selected, the name of the environment variable should be entered in the Host ID field. In 95/98, The environment variable can be assigned a value from the AUTOEXEC.BAT file using the SET command, for example:

SET HOSTNAME=TEST

In NT/2000, you can use the Environment tab in the Properties of My Computer. HOSTNAME is the name of the environment variable. If the string HOSTNAME is entered into the Host ID field, the Host ID will be TEST. A classic use of this feature, is to use the environment variable USERNAME, which Windows automatically assigns a value, which is the name of the user who is logged in.

An environment variable may also be set in Netware Login Scripts (for more information see Section 12.2.3 in your NetOp Manual)

Use Windows computer name

Enable this option if you wish to use your Windows computer name as a Host ID. This feature is useful as it identifies the Host with unique predefined names.

When this option is selected you have the opportunity of prefixing the computer name with the Workgroup name. There is also an option to choose the character that separates the computer and workgroup name. Enter this in the available field.

The Workgroup name option is not available when using Windows NT 3.x

Public Host name

The public Host name option decides whether Guests browsing for Hosts are permitted to find this Host when browsing.


Program Options - Audio

Enable Full Duplex

Select this option to enable full duplex sound for use with the NetOp Audio Chat feature.

Using Full-duplex enables a user at the Guest to talk to and hear a user at the Host PC at the same time. If this option is enabled NetOp will detect whether full-duplex is available and then use it.

Note: Please consult your audio hardware documentation to verify that the particular sound device being used supports the full-duplex sound option.

Silence Level

The silence level thumb adjusts the Audio Chat silence level, which refers to the audio level threshold that must be reached before a particular sound is picked up and used by the NetOp Audio Chat feature.

If full-duplex is not available or not used, NetOp must arbitrate the ownership of the microphone because the Guest and Host can not talk at the same time (similar to a walkie-talkie) i.e. The Guest must stop speaking before the Host can speak and vice-versa. For NetOp to release the ownership of the microphone it must be able to detect silence, which can't be completely attained because of background noise. Experiment with the thumb, by placing it in a position where nothing is sent when you are not talking, and everything is sent when you are talking.

If full duplex is used the silence thumb can be set in a low position so the microphone is turned on all the time. If you are communicating over a slow line (e.g. modem) you might want to experiment with the thumb to limit the bandwidth.

Line Hold

Use this option to configure the amount of audio data sent as "one-unit" across a communications link. For example, if a user is engaged in a normal vocal Audio Chat, the line hold will probably be set to medium or low allowing for both Guest and Host modules to interact with each other without long delay times. The line hold will be set to high if a user wishes to transfer a continuous piece of audio data over the link requiring a continuous stream of information for smooth play.

Check Sound System

Use this option to check the current sound system installed on your PC for use with the NetOp Audio Chat feature.

Note: Before initiating NetOp Audio Chat please make sure that you have configured all sound components and device drivers. For more info please consult your audio device hardware documentation as to available drivers and features of your particular audio device.

Advanced


Program Options - Audio - Advanced

The advanced tab allows you to configure both audio input and output devices. By default NetOp will use the most suitable devices available, in case a PC has more than one sound device installed you may choose one.


Program Options - Help Request

Problem Description

Use this dialog to enter a particular problem description. This description will be sent to the Help Provider chosen by the Host every time the Request Help button is activated from the main Host dialog.

Note: By leaving this field blank you will be prompted to enter a description of the problem you are experiencing every time the Request Help button is activated.

Help Provider

Use this field to enter a name of a NetOp Help Provider. NetOp will attempt to reach the particular Help Provider every time the Request Help Button is activated.

Note: By leaving this particular field blank the user will be presented with a list of available Help Providers every time the Request Help Button is activated.

Communication Profile

By using this option it is possible to define a specific communication profile that will be used for Help Requests exclusively. For example if a Host waits for call using the IPX communications profile, the particular Host may reach a NetOp Help Provider by using the TCP/IP profile instead.

In the communication profile section of the Help Request tab you can choose to either Use current Host communication Profile(s) or Use a specific Communication Profile from the drop down list. When a user activates the Help Request button the specific "Help Request Communication Profile" will be activated.

Phone Number/IP address

Use this field to define a phone number, when using an ISDN, a modem or an outgoing Gateway communication profile. For TCP/IP (TCP) communication profiles, this field is used to specify the IP address of the Guest.

Help request Timeout

By entering a number from 0 to 60 you may specify the length of time (in seconds) in which a Help Request should remain active after it has been forwarded to the Help Provider. By entering  '0' the Help Request will remain active until serviced by the Help Provider or cancelled by the Host user.

Add Help Request icon to tray

Selecting this option will add a Help Request icon to the Host PC's system tray. By clicking this icon the Host will search for available Help Providers (Performing the same function as the Request Help button does in the main Host dialog.).

Note: Hosts running in "Stealth Mode" will be able to request help using the system tray icon, while the main Host dialog remains completely hidden.


Configuration

Host ID

The Host ID is the name used by Guests to identify the Host. The default situation is that this field is automatically filled with the Windows computer name, so you will see a field showing the computer name, but it is greyed out.

If you wish to specify your own string here, select Enter name or leave name field blank in the Host Name tab page of the Program Options dialog. The field will now be enabled and you can type in a string, which is limited to 32 characters.

If an enabled Host ID field is left empty, the Host can still be called by IP address or DNS name when using TCP/IP, and by MAC address when using IPX or NetBIOS.

Communication Profile

This field defines the communication profiles that should be used to communicate with NetOp Guests.

Use the checkboxes to select any communication profile, and have the Host wait for call on the particular profile(s) selected.

For example: A Host can Wait for call on both a modem profile and a TCP/IP profile allowing it to be accessed by Guests on it's LAN or users at remote locations contacting the Host via a modem.

See also:

Program Options

Communication Profiles


Communication Profiles

A communication profile is simply a collection of information about a particular communication device (a protocol or interface NetOp can use for communication (e.g. NetBIOS or serial) ).

By collecting all needed information about a device in a communication profile NetOp makes it easy to quickly switch between communication setups.

NetOp comes with a number of predefined communication profiles, one for each supported device. To maintain the communication profile database select Communication profiles from the Configuration menu. This activates the following dialog box.

The list shows you the existing profiles in the database, which are always sorted alphabetically.

Searching

You can search for a record by pressing a key. For example pressing A will move you to the first profile starting with the letter 'A' (or 'a').

Inserting

If you activate the New button (or press ALT+N), you will add a new record to the database, its contents will be similar to the selected profile's (except for the name which will be blank).

Deleting

You delete profiles by clicking the Delete button (or by pressing ALT+D on your keyboard).

Editing


Quick Guide

To start the Host program, double click on the Host icon in the NetOp program folder or start the program NHSTW32.EXE (NHOSTW.EXE - Windows 3.1x PCs) from the NetOp directory. The first time the NetOp Host is run, it will offer to guide you through configuration of your modem. You may skip or postpone this setup if you wish, you can always define a modem profile.

In the Communication profiles  section in the Host dialog, check a box for each of the profiles you wish the Host to listen on.

Activate the Host by clicking the Wait for call button in the Toolbar. The Host then initializes and waits for incoming calls. Please note that by default this does not happen automatically when you start the program.

To start the Host directly the next time it is loaded, choose Program options from the Host's Configuration menu, and enable Wait for call at program startup. You can also have the Host load automatically when you boot by enabling Load Host at Windows startup.

The Host remembers the setup information for future use.


Security

The NetOp Host includes a number of security features. Use these to prevent unauthorized access to the Host and to limit the number of actions a Guest can perform.

The authentication method is selected in the Guest Access Security dialog from the Configuration menu, choosing the Guest Access Method you wish. You can switch between five different methods

Grant all Guests default access privileges

Grant each Guest individual access privileges using NetOp authentication .

Grant each Guest individual access privileges using Windows authentication

Use NetOp Access Server on Guest side

Use NetOp Access Server on Host side

   Allow Guest to

Password Policy

Call Back

Confirm Access

Maintenance Password

  See also:

 MAC/IP Address List


Security - Individual Access Privileges
Security - Individual Access Privileges using NetOp authentication

This is a more advanced way of configuring security on the Host. When you use individual Guest access privileges based on NetOp authentication, you must specify separate settings for every Guest. For instance you can allow some Guests to remote control keyboard and/or mouse and transfer files and other Guests to only be able to view your screen. A Guest user has to identify himself with a name and a password (if any) when connecting to the Host.

Select Grant each Guest individual access privileges using NetOp authentication in the Guest Access Privileges tab of the Guest Access Security dialog to set this authentication mode. If this option is selected you will see a tree structure in the Individual Guest access privileges assigned section representing the defined Guests.

The folder icons represent security roles specifying access privileges for a group of Guests, which are represented as 'man with kite' icons contained in the folders. Each icon specifies a name and a password (if any) for a Guest.

The right pane of the dialog will change depending on whether a Guest is selected or a security role is selected. The figure below shows the right pane when a guest is selected. The next figure shows the right pane when a security role is selected.

The Host comes with two predefined security roles, but security roles can be added and deleted as you wish. In this example we have added a new role, where we can put people who may not only view the screen, but also pick up files from the Host.

Activate the Add security role to add a new security role. Activate the Add Guest button to add a Guest definition to the active security role folder. Changes to a security role or to a Guest are made by editing the right side pane of the dialog. To rename a Security role or a Guest right click in the list box and select rename in the resulting menu. You can move Guest elements in the hierarchy by using drag and drop with the mouse. If you doubleclick a security role icon, you will expand or collapse the role. If you delete a security role folder, all Guests belonging to this folder are deleted as well.


Security - Profile
Security – Allow Guest to

The section of the security dialog box contains the settings, which describe what actions a Guest is allowed to perform on the Host. The various options available are described here:

Remote Control

Specifies whether a Guest is allowed to start a remote control session.

Note: If both Guest and Host are version 6.x or over, disabling this option will also display the use Keyboard and mouse, Blank the screen, Lock keyboard and mouse, and Boot Host options.

Use Keyboard and mouse

If this option is disabled the Guest will not be able to remote control the Host's keyboard and mouse, but only view the screen. Sometimes referred to as View only.

Lock keyboard and mouse

Specifies whether the Guest is allowed to lock the Host's keyboard and mouse.

Boot Host

Specifies whether the Guest is allowed to boot the Host PC.

Transfer Clipboard

Specifies whether a Guest is allowed to transfer clipboard content to or from the Host.

Blank the screen

Enable this to allow the Guest to blank the screen on the Host.

Chat

Specifies whether the Guest is allowed to start a chat

Audio Chat

Specifies whether the Guest is allowed to start an Audio Chat.

Send files to Host

Specifies whether the Guest is allowed to transfer files from the Guest to the Host.

Receive files from Host

   Specifies whether the Guest is allowed to transfer files from the Host to the Guest

   Redirect Print

   Specifies whether a Guest is allowed to send or receive print jobs from the Host.

See also:

Call back

Confirm Access


Security - MAC/IP Address List

To authenticate a given Guest is calling the Host from a specific PC, NetOp includes a feature enabling only Guests running from PCs with authorized MAC (Media Access Control) addresses or IP addresses can remote control a Host.

On the Host a list can be maintained which holds information about which MAC and IP addresses are permitted to remote control this Host.

Select the MAC/IP Address List Setup tab in the Guest Access Security dialog to define, edit or delete a MAC/IP Address.

 Select the Enable MAC/IP Address Check checkbox to enable this option, and add MAC or IP addresses as described below.  To disable this option simply disable the checkbox.

Adding/Editing


Security - MAC/IP List -Editing

The Guest MAC addresses are entered using a special syntax: 0xnnnnnnnnnnnn , where nnnnnnnnnnnn is the 12-digit hexadecimal burn-in address on the network adapter being used.  For example 0x08005AABD3EF.

The Guest IP addresses have to be entered in dot-decimal notation (i.e. 208.0.0.1).


Security - Password Policy

It is possible to define a password policy on the Host.  This specifies how many password attempts a Guest has and what will happen if the limit is exceeded.

Press the Guest Password Policy button to define a password policy. In the resulting dialog choose the maximum number of wrong passwords a Guest can enter and what action to take if the limit is exceeded: Hang up, Disable (do not take further calls from any Guest) or boot the Host.


Security - Call Back

This setting is only used if the Host is called via dial-up profiles such as Windows modem, Serial or ISDN. Set the call back level in the Call back section of the security dialog. If call back is enabled, the Host will answer incoming calls from a Guest and then hang up and call the Guest back.

The call back facility serves two purposes:

1.	Security: By specifying a Callback number it can be ensured that the Host is only controlled from specific telephone numbers.

2.	Phone charges: Call back can be used to reverse phone charges from Guest to Host.

There are three different settings for call back:

1.	No call back: No call back will be performed.

2.	Call back to: A call back is attempted to the specified number.

3.	Roving call back: The Guest is prompted for the number to call back to.

You might want to instruct the Host to wait a number of seconds before calling back, so your modem can reset itself properly. You can specify this parameter in the Communication Profile Edit dialog for the profile you are using.


Security - Confirm Access

If this option is enabled, the Host will be presented with a dialog box every time a Guest attempts a connection. From this dialog the Host user can accept or deny the remote control attempt.

Enabling confirm access makes sure the Host is not accessed while unattended.

No

Do not confirm access

Always

Confirm access at all times

Only when user logged in

By selecting this option Confirm Access will be enabled only when the user has already logged into Windows.


Confirm Access

A Guest is attempting to connect to your PC, you may either choose to allow the Guest to connect or Deny in which case the Guest will be disconnected from the Host PC.

See also:

Security


Security - Add Guest

Select the name and password the particular Guest should use when logging into the Host. You may also configure a Call Back policy assigned to this Guest.

See also:

Security

Individual Access Privileges


Security - Add User or Group

Select the domain the account (user or group) is in. On Windows NT and Windows 2000, a list of available domains is presented. On Windows 95 and 98, a domain name must be entered manually. When the domain name is chosen, a list of available accounts will appear in the second combo box. Depending on whether a user or a group is being added, the list will contain users or groups. Select the account that should be added in the lower combo box, and click Ok.


Security - Default Access Privileges
Security - Default Access Security

This is the simplest way to configure security. When using default you only specify one set of security settings, which are valid for every Guest connecting to this Host.

A Guest user will not have to identify himself when connecting to the Host but has to enter a password, if one is defined by the Host.

Select Grant all Guests default access privileges in the Guest access privileges tab page of the Guest Access Security dialog to use this mode of security configuration. If this authentication mode is selected, you specify all options directly in the Default access privileges section of the dialog.


Gateway Security

The NetOp Gateway contains advanced security features to prevent against unauthorized access.

The security configuration of the Gateway is divided into Gateway security and Host security.

Gateway security must be passed in order to remote control any Host on the network through the Gateway. In addition the individual Host security settings are still active and must be passed as well. Thus Gateway security can be viewed upon as a firewall, which protects the entire network from unauthorized access.

Host security governs security for the Host part of the Gateway, both for external Guests calling through ISDN or serial/modem to remote control the Gateway and for network Guests which want to control the Gateway PC.

The Gateway security is accessed by activating Gateway Access Privileges from the Configuration menu.

Default Access Privileges

Individual Access Privileges

Password

Call Back


Gateway Security - Individual Access Privileges

This is a more advanced way of configuring the security on the Gateway. Using individual Guest access privileges, you specify separate settings for every Guest. For instance you can allow some Guests to be able to call back to a fixed number and prevent other Guests using the Call-back feature.

A Guest user has to identify himself with a name and a password (if any) when connecting to the Gateway.

Select Guests have individual access privileges in the Guest access privileges section to use this mode of security configuration. If this option is selected you will see a list representing the defined Guests.

Here you can maintain your list of Guests allowed to access the Gateway.

Press the Add button to add a new Guest. You can also edit or delete Guests on the list by highlighting the Guest name and pressing the Edit or Delete buttons.


Gateway Security - Default Access Privileges

This is the simplest way to configure the security. When using default access privileges you only specify one set of security settings, which are used for every Guest connecting to the Gateway.

A Guest user will not have to identify himself with a name when connecting to the Gateway but might have to enter a password if one has been defined.

Select Every Guest has default access privileges in the Guest access privileges section to use this mode of security configuration. If this option is selected you specify the options directly in the Default Guest access privileges section of the dialog box.


Gateway Security - Password

The Gateway can be protected by a password, which a Guest has to enter correctly in order to gain access to the Hosts.

For default privileges you can specify one password, which every Guest must enter before gaining access to any other Hosts on the network. For individual privileges you can choose different passwords for the different Guests. In the Enable section, enable the Password checkbox and enter a password in the field provided.


Gateway Security - Call Back

If call back is enabled, the Gateway will answer incoming calls from a Guest and then hang up and call the Guest back.

The call back facility serves two purposes:

1.	Security: By specifying a callback number it can be ensured that the Host is only controlled from specific telephone numbers.

2.	Phone charges: Call back can be used to reverse phone charges from Guest to Host.

There are three different settings for call back:

1.	No call back: No call back will be performed.

2.	Call back to: A call back is attempted to the specified number.

3.	Roving call back The Guest is prompted for the number to call back to.

When call back is enabled, an option called Wait before Callback will be enabled. Here you can enter the number of seconds to wait before the Gateway initiates the call back session.


Security - Maintenance Password

The Host's settings can be protected by a maintenance password. This option can be configured so a password has to be entered to access various parts of the Host's configuration setup. This ensures the Host user against unauthorized changes to configuration settings (e.g. by a Guest).

Select Maintenance Password from the Configuration menu and a dialog will be displayed.

To define (or change) the maintenance password press the Change Maintenance Password button.

If you wish to assign the maintenance password to other parts of the program, simply enable the check boxes next to each option.  These options are described below:

Guest Access Security

Enable this option if you want the user to enter the maintenance password when selecting Guest Access Security from the Configuration menu.

Gateway Access Privileges

Enable this option if you want the user to enter the maintenance password when selecting Gateway Access Privileges from the Configuration menu. This option is only available if you are using the NetOp Remote Control Gateway module.

All other configuration

Enable this option if you want the user to enter the maintenance password to access the configuration settings on the Host (other than Guest Access Security) such as log setup, program options, the modem database, etc.

Program exit and Stop Host

Enable this option if you want to keep the Host running without user intervention.  If this option is enabled the user will have to enter the maintenance password to stop the Host (if it is running) and to exit the program.

Protect security configuration files

The following three options allow a user to select a particular method in which the Host configuration files should be protected. These files store security and other configuration settings. The three options offered are as follows:

Protect by maintenance password only (if applies)

By selecting this option, Host configuration files will be protected only by a maintenance password.

Protected files when connected

By selecting this option, all Host configuration files will be protected while a connection is established with a Guest. This will prevent users from deleting, overwriting, or otherwise tampering with the files. You may use this option in conjunction with maintenance password protection.

Protected files when connected and waiting for call

By selecting this option, all Host configuration files will be protected while a connection is established with a Guest, and while the Host is waiting for call. This will prevent users from deleting, overwriting, or otherwise tampering with the files. You may use this option in conjunction with maintenance password protection.


Security - Maintenance Password - Change

Enter your old password (empty for no previous password) in the Old password field, enter your new password in the New password field and finally re-enter your new password in the Confirm password field.


Chat

The chat function brings up a window on the Host and Guest, which allows the users to communicate.

To start a chat session with the Guest, choose Chat from the Utilities menu or activate the chat button in the Toolbar (see the following figure).

Similar dialogs will be displayed on the Host and Guest. Everything typed on the Host and Guest will be communicated between the users and displayed in the dialog boxes.

Please note that chat has to be enabled in the Host security settings, otherwise the chat button and the chat menu item will be disabled.


Chat Dialog

Use this dialog to chat with a Guest. Similar dialogs will be displayed on the Host and Guest. Everything typed on the Host and Guest will be communicated between the users and displayed in the dialog boxes.

Please note that chat has to be enabled in the Host security settings, otherwise the chat button and the chat menu item will be disabled.


Help Request

The Host user can activate the Request Help button in the Toolbar (see the following figure), or select Request help in the Utilities menu to initiate a Help request to any registered help provider

You can only request help if you have initialized communication by activating the Wait for call button.

When the call for help function is activated the Host browses the network for help providers. If any help providers are found, the following dialog box appears:

Enter a description and choose a help service. The help services appearing in the list are the ones registered by the Guests providing help on the network. Press Select, the request is now registered.

Whenever a call for help is made the request appears on the screen of the help providing Guest(s). When a Guest handles the request a remote control session is automatically started between the help-providing Guest and the help-requesting Host.

A Host can only have one pending help request. To cancel a pending request, activate the Cancel Help button in the Toolbar (see the following figure), or select Cancel help from the Utilities menu.

It is also possible to have the Host direct a predefined Help Request  description to a specific NetOp Help Provider.

When a Help Request is made after it has been predefined in the Host options section, the NetOp program will forward only the specified problem description to the predefined Help Provider.


Tool Bar

In the Toolbar (which is placed below the menu bar) shortcut buttons for the most common commands are available. Select one of the following options


Communication Profiles - Gateway Specific

When editing a NetOp Gateway communication profile, some extra features are available for editing to help identify particular Gateway functionality. These features are the NetOp Nets, Device Groups and Call Direction option. The following section focuses on the Gateway Specific Settings and proper configuration and troubleshooting methods that will insure the Gateway works properly.

Device Groups

A Device Group associates dial-up communication profiles such as TCP/IP (TCP), ISDN (CAPI), Windows Modem, Serial or Infrared on different Gateways. This is done to help group particular devices for the purpose of routing outgoing calls.

When a Guest chooses a Gateway communication profile in order to make an outgoing call he is presented with the option of choosing a Device Group or Browsing for Device Groups.

The Device Group identifies the dial-up profile on a Gateway (or multiple Gateways) that is used to reach a particular Host or Hosts at a remote location.

   NetOp Nets

When you select a communication profile from the communication device section of the main Gateway dialog, a number will appear to the right of the profile. This number is referred to as the NetOp Net. This number can be changed  by editing the Gateway Settings section of the communication profile.

Normally these fields need not be changed.

It is only necessary to alter the NetOp Net numbers in a situation where there are multiple incoming Gateway PCs on a single network. In this situation the following rules apply:

1. The NetOp net number that is attached to the network protocol must be the same on all the incoming Gateways attached to the network. A NetOp net number assigned to a network protocol must be different from every NetOp net number attached to a dial-up protocol.

2. The NetOp net number for the dial-up protocol must be unique on every incoming Gateway and it must be different from the NetOp net number attached to the network protocols.

3. NetOp net numbers must have a value between 10 and 127.

Other than that, the NetOp net numbers can be arbitrarily chosen. NetOp uses net numbers from 100 as default for the first communication profile selected and then continues in sequence for all later profiles.

Example

A network has three Gateways attached to it. On all three Gateways, the NetOp net number for the Network protocol (IPX) is set to 101. The NetOp net number for the Dial-up protocol (Modem) is set to 102 on the first Gateway, 103 on the second and 104 on the third.

Call Direction

Specifies weather the Gateway will allow for incoming calls, outgoing calls or both.

Incoming and outgoing calls: When this option is selected the NetOp Gateway will allow for incoming calls from remote locations (using the TCP/IP (TCP), Windows modem, Serial, ISDN interfaces or Infrared), and for outgoing calls originating at the Gateway's own network (using IPX, TCP/IP (UDP) and NetBIOS)

Outgoing calls only: Select this option to allow only outgoing calls originating from the Gateway's own network (using IPX, TCP/IP (UDP) and NetBIOS).

Incoming calls only: When this option is selected the Gateway will allow for incoming calls from remote locations (using the TCP/IP (TCP), Windows modem, Serial, ISDN or Infrared interfaces) only.

Note: The Device Group and Call Direction options can only be changed when editing a Dial-Up communication profile (TCP/IP (TCP), ISDN (CAPI),Windows Modem, Serial, Infrared).

  Selecting Gateway Communication Profiles

As in the NetOp Host module, it is possible to select more than one communication profile for the NetOp Gateway. For example, a Gateway can be contacted via modem allowing a remote Guest to browse and control Hosts using IPX, NetBIOS and TCP/IP (UDP) without disconnecting. By the same logic a Guest using a networking protocol (IPX, TCP/IP (UDP), or NetBIOS) to call the Gateway can establish a session with a remote Host using a dial-up communication profile (TCP/IP (TCP), ISDN (CAPI), Windows modem, Serial or Infrared) through the Gateway. This can be done by selecting the appropriate communication profiles check box in the communication device section of the main Gateway dialog.

It is also possible to setup multiple lines to connect to one Gateway PC. This is particularly useful when more than one Guest wishes to connect to the Gateway or when the Gateway will be accessed by  more than one Guest simultaneously to remote control Hosts using a dial-up communication profile. For example, if your machine has two COM ports, it is possible to connect two modems (which are connected to two separate lines) and allow two different Guests to use the Gateway for connecting to their networked PC's.

As in the standard NetOp Host, the communication profiles used by the Gateway are selected at the main Gateway dialog

The selected communication profiles are marked by a check-mark.


Help Request - Device Groups

From this dialog select the Gateway Device Group that should forward this particular Help Request to a registered Help Provider.

More info:

Help Request

Gateway Specific Settings


Help - About

The About-dialog displays information such as the NetOp version and build number currently installed. Plus license name and serial number information.

From this dialog you may also navigate to the System Information dialog.


Help - System Information

This dialog displays various configuration information about your PC.


Access Server - Enable

Select this option to enable the Access Server Program. To configure the program you will need to start the Access Server Configuration Program, located in your installation directory.


Remote Printing

The NetOp Remote Print facility allows a Host to send a print job to a Guest where it will be printed locally and vice-versa. This option is available for Windows 95/98 and Windows NT 4/2000. To utilize this facility you must first add a NetOp printer using the Program Options   .

Once a connection has been established, a user at the Guest PC can print from any application to the Host PC by choosing one of the NetOp Remote Control Printers which have been added in the Remote Control Program Options, depending on the settings you have chosen, the print job will be either sent directly to the Host's default printer or a dialog box will be displayed listing all printers available on the Host, you can then choose to which the print job should be redirected to.

If you are printing from a NetOp Guest connected to more than one host, you are always prompted with a list of hosts to choose between. You can't redirect one print job to several Hosts simultaneously.

DOS Printing

To redirect a print job from a DOS application on the Guest PC to a Host printer you must do the following:

Windows NT 4 and Windows 2000

Share the NetOp printer as for example "myprinter". Then, from the command line in a DOS box, type the command below, where "mypc" is the name of your computer and "myprinter" is the name you shared the printer with. The reason for sharing the printer is only to enable the "net use" command to detect it, not to share it with others. If you do not share the printer, "net use" rejects to operate on the printer.

net use lpt1: \\mypc\myprinter /persistent:yes

Windows 98/95

Utilize the NRPWATCH.EXE program located in the NetOp directory. Open a DOS command prompt, CD to the NetOp install directory and type NRPWATCH for an explanation of its usage. NRPWATCH requires that your third party application can print to a file instead of directly to a port.

Basically, NRPWATCH listens for files being saved in a directory of your choice. When a file is saved here, it detects it, prints it to a printer of your choice and deletes it. If the printer you choose is a NetOp printer, and if a NetOp connection is open, NRPWATCH will print your file on a remote printer.

If you wish a permanent setup, find a suitable command line and add it to your Windows startup section

Note: It is highly recommended that print jobs should be redirected between Printers utilizing the same drivers.


Online Support

NetOp 6.5 now provides an Online Support option. By clicking on HELP and then selecting ONLINE SUPPORT you will be able to view the latest support information on http://www.danware.com, and also to request support .


Program Options - Connection Notification

The Connection Notification settings provide means for notifying the Host user about connections. The Connection Notification settings are divided into three groups:

Upon connection

•	Play a sound.

•	Display a notification message dialog

•	The dialog can be password protected from being removed.

During connection

•	Play a sound with a regular interval, which you may specify in seconds

•	Display the Guest's name in the title bar

After connection

•	Display a notification message dialog.

•	The dialog can be password protected from being removed.


Security - Individual Access Privileges using Windows authentication

This is a security access method similar to Individual Access Privileges using NetOp Authentication. But this method is integrated with the Windows security management and leaves most of the administration of guests and passwords to Windows.

When using Windows security management, the NetOp Guests are identified by their Windows user accounts in a Windows NT/2000 domain or local accounts on the Host computer. Only Windows NT/2000 Hosts can use locally defined accounts.

In order to connect to a Host, the Guest user has to enter the Windows login name (the user name) and the corresponding password. When using Windows security management with NetOp, Guests connecting to a Host are referred to as users, meaning users in the Windows security management terminology. Windows can arrange users into groups of users. NetOp handles users and groups the same way.

Select Grant each Guest Individual Access Privileges using Windows Security Management in the Guest Access Method drop down list to use this method. If this option is selected, you will see a tree structure in the Individual Guest access privileges section representing a directory listing of users and groups who can call this host.

The folder icons represent security roles, specifying access settings for a number of users or a number of groups belonging to the security role folder. The right pane of the dialog will change depending on whether a user/group is selected or a security role is selected.

The Host comes with two predefined security roles, but security roles can be added and deleted as you wish. Deleting a Security role folder will also delete all user and group references belonging to this folder, from the listing. Deleting user or group references from the list does not delete the accounts from Windows itself.

Activate the Add security role to add a new Security role. Activate the Add User button to add a user reference to the active security role folder and activate the Add Group button to add a Group reference to the active security role folder.

When activating the Add User button or the Add Group button, a dialog appears. First, select the domain the account (user or group) is in. On Windows NT and Windows 2000, a list of available domains is presented. On Windows 95 and 98, a domain name must be entered manually. When the domain name is chosen, a list of available accounts will appear in the second combo box. Depending on whether a user or a group is being added, the list will contain users or groups. Select the account that should be added in the lower combo box, and click Ok.

Changes to a security role, a user or a group are made by editing the right side pane of the dialog. To rename a security role, right click in the list box and select rename in the resulting menu.

You can move user and group elements in the hierarchy by using drag and drop with the mouse. By double clicking on a security role icon, you will expand and collapse it (Show/hide Guests).

If you have administrator privileges on Windows NT or Windows 2000, click the Windows User Manager button to add or delete users or groups.

Settings for Security Roles

A security role defines a set of access privileges such as:

•	Allow guests belonging to this role to remote control this PC.

•	Always to present a Confirm access messages to the Host user

A user can be a member of several security roles either directly (via user name) or implicitly through the membership of a group. This means, that a user can belong both to a security role where Remote Control is enabled and to another security role where Remote Control is disabled at the same time. The following describes how the different settings are combined.

All settings in the Allow guest to group are or'ed together. Hence, if the user belongs both to a Security role where Remote Control is enabled and to another security role where Remote Control is disabled, the user is allowed to remote control the Host. On the other hand the Confirm access settings are and'ed together. Consequently, if the user belongs to a security role where Confirm access is enabled and another security role where Confirm access is disabled, the user is allowed to connect to the Host without Confirm access.

Settings for Users and Groups

It is not needed to define passwords in this authentication mode, because NetOp will use the password validation available in the Windows security management.

Callback settings can be applied to a user or group. Because a user can appear several times in the list (either directly or indirectly),  special rules apply to how callback information is extracted. The callback information is taken from the first occurrence of the user. If the user is not found, because the access to the Host is available through the membership of a group, the callback information is taken from the first occurrence of a group, which the user is a member of.

If access to the Host is controlled through membership of groups, and individual callback information is needed, add a security role at the top of the list without any privileges, and enable Confirm Access. Add users to this security role, and specify the necessary callback information.

On Windows NT 4 and Windows 2000, NetOp can collect the callback information from Windows Remote Access Services (RAS). If Get callback information from Windows NT Remote Access Services (RAS) is checked, NetOp will collect callback information from RAS, and the callback section in the dialog will be hidden. Please note that callback information can be specified in RAS without granting RAS access for the user. The RAS settings are also referred to as Dialin information in Windows.


Security - Use a NetOp Access Server on Guest Side

The NetOp product family includes a module for central security management of Guest access to Hosts – the NetOp Access Server. The NetOp Access Server is a special Host module that can be used to manage Host security and Guest privileges.

Select Use NetOp Access Server on Guest side in the Guest Access Method drop down list to use this method of authentication. Select this Guest access method if you want the Guest to be authenticated by an Access Server before trying to take control of this Host.

The Guest will have to locate an Access Server on its own network, be authenticated and retrieve the access privileges it has when controlling this Host.

The option Use authentication key string is used to assure the validity of the Access Server and that the Guest is authenticated by an Access Server that the Host trusts.


Security - Use a NetOp Access Server on Host Side

The NetOp product family includes a module for central security management of Guest access to Hosts – the NetOp Access Server. The NetOp Access Server is a special Host module that can be used to manage Host security and Guest privileges

Select Use NetOp Access Server on Host side in the Guest Access Method drop down list to use this method of authentication. Select this access method if you want the Host to authenticate the Guest on an Access Server when the Guest tries to take control of this Host.

With this option, the Host will have to locate the Access Server, on its own network rather than on the Guest's network. The Host will authenticate the Guest on the Access Server and retrieve the access privileges the Guest has when controlling this Host.

The option Use authentication key string is used to assure the validity of the Access Server. The second option Use Access Server with MAC/IP address is used to ensure that the Access Server is situated on a certain MAC/IP address. This option could also be used in a situation where the Host is unable to find the Access Server (e.g. if the Access Server is located on a different TCP/IP segment).

The first time the Host needs an Access Server to authenticate a Guest it will locate one with a matching authentication key. All subsequent authentication calls will go to this Access Server until it's no longer available. The Host will now try to locate a new Access Server with the same authentication key. This allows a fault tolerant configuration, but requires that the option Use Access Server with MAC/IP address is blank.


Connection Notification - Upon Connection

This dialog is shown because a NetOp Guest running on another computer has connected. This Guest is remote controlling your computer right now, or is having a chat, audio chat or file manager connection. The name of the Guest is noted in the dialog. When the Guest ends the session, this dialog will disappear automatically. If you have also specified that you want to be notified when Guests hang up, there will be another dialog at that time.

The dialog has a password field, because you might not want the Guest to remove it.


Connection Notification - After Connection

This dialog is shown because one or more NetOp Guests have been connected to your computer, and has hung up. The Guests may have been remote controlling your computer, or may have made chat, audio chat or file manager connections. The names of all the Guests are noted in the dialog.

The dialog has a password field, because you might not want the Guest to remove it.


For Administrators Only
For Administrators

The following four sections may contain valuable information about NT/2000 services and processes for people with insight in operating system features

Service and Process Security in NetOp Remote Control, Main Processes

The NetOp Helper Service, Windows NT and 2000

Service and Process security in NetOp Remote Control, Overview, Windows NT and 2000

The NetOpActivity Local Group, Windows NT and 2000


For Administrators 1
Service and Process Security in NetOp Remote Control, Main Processes

Fundamentals

The main Host processes include NHSTW32.EXE, NGWW32.EXE, NLOGW32.EXE, NACCSW32.EXE, NNSW32.EXE, NLDRW32.EXE, NUTIL32B.EXE, VITAWRAP.EXE, some instances of NHOSTSVC.EXE, and in some rare situations NGSTW32.EXE.

These processes form the bulk of the Host functionality of NetOp Remote Control.

These processes run in the secure context of the interactively logged on user modified with the NetOpActivity group, as described below.

When a user is interactively logged on to the computer console

The main processes run in the security context of the logged on user, except that the access token also lists membership of the NetOpActivity group.  This extra group membership applies only to operations on the same computer, Network operations and a few other system operations will ignore it.

Note that because NetOp Remote Control is a remote control product, rather than a traditional server service, Guest induced operations such as file transfer are performed in the context of the logged on user, rather than in a context derived from the identity (if any) stated when establishing the connection.

When no user is logged on, or the logged on user cannot be determined

The main processes run in a synthesized local security context defined as follows:

•	User ID:  Anonymous logon (S-1-5-7).

•	Groups: NetOpActivity, Everyone (S-1-1-0), INTERACTIVE (S-1-5-4), Users (S-1-5-32-545, Windows 2000 only).

•	Privileges: SeChangeNotifyPrivilege, SeShutdownPrivilege.

•	Default owner: NetOpActivity, in a few cases Anonymous logon (S-1-5-7).

•	Default group: NetOpActivity.

•	Default ACL: LocalSystem - Full Access, NetOpActivity - Full Access.

•	Network credentials: None

Note that because NetOp Remote Control is a remote control product, rather than a traditional server service, Guest induced operations such as file transfer are performed in the context of the logged on user, rather than in a context derived from the identity (if any) stated when establishing the connection.

When the security has been explicitly disabled by a system administrator:

A system administrator may turn off the process security on the main processes by setting the following secured registry value:

   Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetOp Host for NT Service\SecurityLevel
   Value: LowLevel = 1 or Yes or True

When this has been done, the Main processes will run with full LocalSystem privileges, giving almost unlimited system access, but no direct network access.  Also, if the host program is started manually, it may arbitrarily choose to run as either LocalSystem or the user who started it, until that user logs off, at which point it will be terminated by the system and a fresh copy loaded under the LocalSystem account.

Setting this value should only be done to solve special problems under the direction of Danware technical support, and it should be undone as soon as it is no longer necessary.


For Administrators - 2
The NetOp Helper Service, Windows NT and 2000

The NetOp Helper Service is located entirely in the program file NHOSTSVC.EXE.  Not all processes by this name are part of the NetOp Helper Service.

This very small service has been carefully written for extra high security.  It is the only component of a running NetOp Remote Control system, which runs in the powerful LocalSystem context.  The sole purpose and functionality of the NetOp Helper Service is to
perform selected privileged operations on behalf of the other processes in NetOp, it is designed to resist attempts to use it for any other purpose.

The NetOp Helper Service must be configured to run under the LocalSystem account with permission to interact with the desktop, any other configuration will probably either fail or actually reduce security.

Please notice, that the bulk of NetOp Remote Control runs in a different security context.

Useful things to do to the NetOp Helper Service

If you stop the NetOp Helper Service using control panel, Server manager or other management tools, the service will automatically terminate the main host process before the service itself terminates.  This action is logged in the system Application log.

If you start the NetOp Helper Service using the same tools, it will redo any actions it normally performs at system boot.

Stopping, and then immediately starting the NetOp Helper Service is a useful technique for restarting the main host processes remotely or through a batch file.

Note that the registry name of the NetOp Helper service is "NetOp Host for NT Service".

A useful two line batch file is:

NET STOP "NetOp Host for NT Service"
NET START "NetOp Host for NT Service"

What the NetOp Helper Service does at boot or when started:

•	Repair some of the security and device settings created during setup, if they appear to be damaged.

•	Check if any of the administratively installed copies of NetOp are configured to "run as service"

•	Load the first such copy of NetOp, and keep it loaded in case it is accidentally killed.

•	Repeat most of the process whenever the user logs off, or if the NetOp process appears to be killed by the system.

Why the NetOp Helper Service needs LocalSystem privileges:

The NetOp Helper Service uses the LocalSystem privileges to provide the following key services to NetOp:

•	Access the desktop, even when no user is logged on.

•	Access the secure logon screen for purposes of remote control.

•	Create the special security context for the main NetOp processes.

•	Grant the special rights to the NetOpActivity local group.

•	Perform a few other security operations on behalf of NetOp.


For Administrators - 3
Service and Process security in NetOp Remote Control, Overview, Windows NT and 2000

NetOp Remote Control consists of 3 sets of processes, each running in a different security context, that is with a different access token.

The main Host processes

This includes NHSTW32.EXE, NGWW32.EXE, NLOGW32.EXE, NACCSW32.EXE, NNSW32.EXE, NLDRW32.EXE, NUTIL32B.EXE, VITAWRAP.EXE, some instances of NHOSTSVC.EXE, and in some rare situations NGSTW32.EXE.

These processes form the bulk of the Host functionality of NetOp Remote Control.

These processes run in the secure context of the interactively logged on user modified with the NetOpActivity group.

The ordinary user programs

This includes NGSTW32.EXE (The Guest), NACFGW32.EXE (The Access Server configuration program), SETUP.EXE (The interactive installation program) etc.

These are ordinary user programs running in the security context of whatever logged on user runs them.  They are not treated any different than e.g. NOTEPAD.EXE.

The NetOp Helper Service:

This includes only NHOSTSVC.EXE, and only some of its running instances.

This very small service has been carefully written for extra high security.  It is the only component of a running NetOp Remote Control system which runs in the powerful LocalSystem context.  The sole purpose and functionality of the NetOp Helper service is to
perform selected privileged operations on behalf of the other processes in NetOp, it is designed to resist attempts to use it for any other purpose.

The NetOp Helper Service must be configured to run under the LocalSystem account with permission to interact with the desktop, any other configuration will probably either fail or actually reduce security.


For Administrators - 4
The NetOpActivity Local Group, Windows NT and 2000

As part of its Service and Process security, NetOp Remote Control creates a special local group on each machine where it is installed.  This local group is always called NetOpActivity.  The sole purpose of the NetOpActivity local group is to be granted access to resources, which are needed by the main host processes, but should not be available to any similar process or user.

For these reasons, do not add any users or groups to NetOpActivity, leave it completely empty and do not delete or rename it.

The rights automatically granted to NetOpActivity currently are:

•	Access to the interactive desktop, even when no user is logged in.

•	Read/execute access to the necessary NetOp program files.

•	Read/execute access to selected system DLLs needed to run the main host processes.

•	Write access to selected NetOp configuration files (.NDB files) needed during normal operations.

•	Add and List access to the NetOp program directory (needed to update the selected .NDB files).

•	Read access to the NetOp.INI file in the %SystemRoot% directory (but not other access to the system directories).

•	Access to most in memory objects created by the main host processes, including the process objects themselves.

The following rights are granted to the local Administrators group, to which LocalSystem implicitly belongs:

•	Full Control of the Registry Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetOp Host for NT Service\SecurityLevel.

•	Full Control of the Registry Key HKEY_LOCAL_MACHINE\SOFTWARE\Danware Data A/S\NetOp Family.

•	Read/Execute access to the NetOp program directory.

•	Read/Execute access to the NetOp program and configuration files to which NetOpActivity is granted access above.

Most of these rights are granted by some self-repair features, which are invoked at various times during normal operations.


Marker Mode

The NetOp Marker Utility is a program, which can draw graphic markers like lines and rectangles on the Host screen. You can move the markers around, and you can delete them one by one or clear them all.  The marker utility is installed with the Host module and runs on the Host computer. The marker utility runs on Windows 98, Windows NT4 and Windows 2000. It is not supported on Windows 95.

You start and stop the marker utility from an icon on the Guest's remote control toolbar after a remote control session has been opened. When you click the marker button, the marker utility interface pops up in the upper left corner of the Host's display. The interface has icons for each of the possible graphic elements plus for "Undo" and "Clear". You can draw markers with the Host's mouse or with the Guest's mouse. The marker elements are:

•	Straight lines

•	Freehand line

•	Rectangle

•	Ellipse

•	Arrow

You start drawing a marker by clicking its icon. The pointer will now change shape. Move the cursor to the start point and follow the instructions below for each single marker. When done drawing a marker, you must click an icon again, if you wish to draw another marker.

Drawing straight lines

At the start point, click MB1 (the left mouse button for right handed people). Move the pointer to the next point on your polyline, and click MB1 again. Repeat this as many times as you wish. When you want to end the line, press MB2 (the right mouse button for right handed people).

Drawing freehand

At the start point, press MB1 and keep it down. Move the pointer around with the mouse, and a line will be drawn following the pointer. Release the mouse button when you are done.

Drawing a rectangle

At the start point press MB1 and keep it down. Drag out the desired rectangle, and release the mouse button when done.

Drawing an ellipse

At the start point press MB1 and keep it down. Drag out the desired ellipse, and release the mouse button when done.

Drawing an arrow

At the start point press MB1 and keep it down. Drag out the desired arrow, and release the mouse button when done.

Color and Width

Below the toolbar, you will find two combo boxes, one for color and one for width. The selected color and width will apply to the next graphic element you create. The color and width of the elements you have already drawn, can be changed by right clicking each element, then selecting the new properties in the menus which appear. The size and shape of elements can't be changed, neither can you rotate them.

Deleting elements

You can delete an element by selecting the Undo command from the menu which pops up, when you right-click it. If you choose Clear all instead of Undo, all elements are erased. Undo and Clear all are also buttons in the toolbar. Here the Undo button will delete the selected element. When you draw an element, it becomes the selected one. If you later click on an element with MB1 or MB2, that element becomes the selected element. When an element is deleted, the element last drawn becomes the selected element.

Minimizing the User Interface

When you minimize the NetOp Marker Utility, it places an icon in your icon tray, showing the kind of graphic element last drawn. If you click with MB1 on this icon, the same happens, as if you had clicked the corresponding icon in the toolbar. If you click with MB2, you have the option of restoring the original interface or drawing any specific graphic element.


Communication Profiles - IPX

Description

IPX (Internetwork Packet Exchange) is Novell's network protocol. This protocol is typically used in Novell Netware environments.

Configuration

IPX is usually installed as part of a  network client. If there are any problems with accessing IPX, please contact your network administrator.

Device Specific Settings

To communicate with NetOp for Windows or NetOp for OS/2 Hosts use the IPX device. To communicate with DOS Hosts (NetOp 4.3x RemPCs) use the RemPCIPX v 4.3 device (this device is only available on NetOp for Windows Guests).

A Novell network consists of one or more sub-networks. Each of these sub-networks has an 8-digit hexadecimal number. The NetOp Guest must know the number of a subnetwork to communicate with a PC on that network.

The IPX device specific settings deal with interconnected sub-networks. NetOp provides three alternatives to handling multiple networks:

Local network only

If this option is chosen NetOp will only be able to communicate with PCs, which reside on the same subnetwork as itself.

User defined list of networks

If this option is chosen NetOp will be able to communicate with PCs residing on one of the networks which is specified in the Network list .

Build list of known networks (default)

If this option is chosen NetOp communicates with a Netware server to obtain a list of all the interconnected subnetworks.

To use this option you must have the DLL file NWIPXSPX.DLL available on your computer (Only Win 3.1x NT 3.x).

Host ID format

When configuring the Host a Host ID can be entered. The Host ID should be a string with a maximum length of 32 characters.

If no Host ID is entered NetOp will use the burnt-in network adapter address (typically the MAC address). To call a Host, which uses the burnt-in address as a Host ID, enter 0xnnnnnnnnnnnn. Where nnnnnnnnnnnn is a 12 digit hexadecimal number

(e.g. 0x080005AF341A).


Communication Profile - IPX - Network List

Normally the Guest will automatically communicate with a Netware server to obtain a list of all sub-networks. However there are some situations where this is not desirable:

1.Some Netware installations do not support the automatic building of a subnetwork list.

2.In large complex networks you might want to look for Host PCs on certain sub-networks only, or limit the Hosts call for help feature to certain sub-networks.

In these situations you can maintain a manual list of networks where you want NetOp to look for PCs:

1.Select Communication profiles from the Guest's Configuration menu.

2.Select the communication profile you want to use (must have IPX as communication device) and activate the Edit button (or press New to create a new profile).

3.In the IPX section of the dialog box set Novell networks to User defined list of networks.

Activate the Network list button.

Activate the Add button to add a subnetwork to the list. Press Delete to delete the selected subnetwork, press Edit to modify the number of the selected subnetwork.

To find the network number for a given computer, use Novell's NLIST (Netware 4.x) and USERLIST (Netware 3.x) utilities by issuing the following commands at a command prompt:

nlist user=NetwareLoginName /a ENTER

userlist /a ENTER

Where NetwareLoginName should be substituted with the user's Netware login name. The Address field of the resulting listing contains the network number.


Communication Profiles - NetBIOS

Description

NetBIOS was once one of the most popular protocols for LAN communication. The NetBIOS protocol is typically used in LAN Server, LAN Manager, LANTastic, and Windows NT Server environments.

Device Specific Settings

To communicate with NetOp for Windows or NetOp for OS/2 Hosts use the NetBIOS device. To communicate with DOS Hosts  (NetOp 4.3x RemPCs), use the RemPCNB v4.3 device (this device is only available on NetOp for Windows Guests).

The communication profile edit dialog contains one specific setting when the communication device is set to NetBIOS - the adapter number. The adapter number is defined in the NetBIOS.

NetOp will try to detect which adapter numbers are present on your machine and also tell you which type of NetBIOS is being used. To view this information, press the List button in the NetBIOS communication profile setup.

Host ID format

When configuring the Host a Host ID can be entered. The Host ID should be a string with a maximum length of 32 characters.

If no Host ID is entered NetOp will use the burnt-in network adapter address (typically the MAC address). To call a Host, which uses the burnt-in address as a Host ID, enter 0xnnnnnnnnnnnn. Where nnnnnnnnnnnn is a 12 digit hexadecimal number

(e.g. 0x080005AF341A).


Communication Profiles - TCP/IP
Communication Profiles - TCP/IP (UDP)

Description

IP is a networking protocol increasingly popular in LAN/WAN environments. It is also the protocol used on the Internet. NetOp supports any 100% WinSock 1.1 compatible implementation.

NetOp has two communication devices based on IP, TCP/IP (UDP) and TCP/IP (TCP). The UDP based version uses UDP ports, and because it is not based on point-to-point TCP, it is capable of browsing.

Device Specific Settings

There are two device specific settings in the Communication Profile Edit dialog when using TCP/IP (UDP). The first is max packet size. This lets you change the size of data packets transmitted between Host and Guest. Normally you need not change this setting, because NetOp will automatically find a suitable size. If you experience trouble, try lowering the maximum packet size to for example 512.

Optimize for Internet communication means that NetOp will use 3 MB for the bitmap mode cache and make Automatic compression mean High. Otherwise Automatic compression defaults to low compression on TCP/IP.

Under TCP/IP (UDP) there are some special considerations for NetOp's browse operations (Guests looking for Hosts, Hosts looking for help providers). Since IP networks are typically very large (e.g. the Internet), it normally makes sense to browse only parts of an IP network.

IP Address broadcast list

Advanced


Communication Profiles - TCP/IP - Broadcast List
Communication Profiles - TCP/IP (UDP) - Broadcast List

IP Address Broadcast List

NetOp's default behavior is to browse for all PCs, which are reachable with the reserved IP address 255.255.255.255. You may configure this setting and create your own unique IP address broadcast list by clicking on the IP Address Broadcast List button. This will bring up a dialog box.

Adding / Deleting IP Addresses

To add an IP address to the automatically updated list of addresses where NetOp should browse for PCs press the Add button. In the resulting dialog enter the IP address you wish to add and press OK.

Disable local subnet broadcast

Selecting this option will prevent NetOp from using the reserved IP Address 255.255.255.255 to send broadcasts on the local subnet. NetOp will only use the IP addresses added to the list by the user for TCP/IP communication. Selecting this option will in some cases reduce bandwidth taken up by broadcasts.


Communication Profiles - TCP/IP - Advanced

In the Advanced TCP/IP (valid for both UDP and TCP) configuration dialog, it is possible to select the IP address for this communication profile. This means that if your computer has more than one IP address you can force NetOp to use a specific IP Address. You may even create a communication profile for each address and use these either simultaneously or one at a time, or use a single profile for all your addresses (this is the default).

You may also change the default (6502) port number to another number by un-checking the Use default port numbers check box. The "Receive" port is your own port number, and the "Send" port is the port you expect other NetOp machines to receive on. When using the UDP based device, you can set the port number to zero to have NetOp dynamically assign arbitrary free numbers at runtime.

This option makes it possible to communicate through firewalls and routers that change the port number on the packets that pass through.

Beware, however, that NetOp cannot simultaneously communicate with two machines that have the same IP address as seen from those two machines.


Communication Profiles - ISDN

NetOp for Windows supports two type of ISDN protocols

16-bit (Windows 3.x)

CAPI version 1.1, profile A (e.g. works with EuroISDN DSS1, German national ISDN 1TR6, French ISDN VN2, Belgian ISDN CT1, etc) or CAPI 2.0 interface.

32-bit (Windows 2000/NT/98/95)

CAPI 2.0

Configuration

ISDN CAPI (Common Applications Programmer's Interface) is a driver provided by your ISDN adapter mfg. (As most adapters support the CAPI interface you should still make sure the particular card you are using offers support for the CAPI version you will use with NetOp)

ISDN CAPI must be loaded before you try to access it from the Guest, the Host or the gateway. If you cannot access ISDN CAPI from NetOp, please verify that a supported version is installed and loaded. Please note that a CAPI.DLL must be present.

For CAPI 2.0 the DLL is called CAPI20.DLL except on Windows NT 3.51 and NT 4.0 where it is called CAPI2032.DLL.


Communication Profiles - CAPI 1.1

Local Number

Enter the local number (EAZ) as defined in your CAPI setup.

Short hold mode

Select this to permit the use of short-hold mode. When no data is transferred between the Guest and Host, the line will be disconnected. When activity starts on either the Guest or the Host, the connection will be reestablished. On the Guest there will be an additional time out field next to the short hold mode check box. In this field you specify the number of seconds that can pass without activity before the line is taken down.

This setting must be enabled on both Guest and Host to take effect.

Use of 2 B channels

Select this to permit the Guest to use 2 B channels. If two B channels are available this will increase the raw data speed from 64 kbit/s to 128 kbit/s.

This setting must be enabled on both Guest and Host to take effect.

ISDN Number check


Communication Profiles - ISDN - Number Check

If enabled, only those Guests that have an ISDN number matching a number in this list will be able to access this Host.

This setting is only available on the Host.


Communication Profiles - ISDN - CAPI 2.0

The following figure displays the communication profile edit dialog using the ISDN (CAPI 2.0) specific settings.

Own Number

Specify your own telephone number in the Own number field if your are using short hold mode.

CAPI 1.1

This device drives CAPI 2.0, which is not compatible with CAPI 1.1. If you have CAPI 1.1 installed, you must set B3PROTOCOL=1 in the [ISDN] section of NETOP.INI. You can make connections between CAPI 1.1 on Windows 3.x and this device.


Communication Profiles - Modem

NetOp offers two ways to communicate via a modem

Windows Modem - This communication profile will be available only on 32-bit systems (Windows NT, Windows 95/98).

Serial - Available both on 32-bit and 16-bit systems (Windows 3.x)

On both 32 and 16 bit systems NetOp will lead the user through the configuration of the modem the first time it is started. By default NetOp will use Windows Modem on 32-bit systems and Serial on 16-bit systems.

Note: Windows Modem and Serial Communication Profiles can communicate with each other


Communication Profiles - Windows Modem

Description

The Windows Modem is used to communicate via a modem or another telephony device that has been properly set up in Windows. For the Windows Modem communication profile NetOp uses TAPI or the Telephony API, which is commonly used by programs to make data/fax/voice calls, including the Windows 2000/NT/95/98 programs HyperTerminal, Dial-up Networking, Phone Dialer, and other Win32® communications applications written for Windows 2000, NT, 98 and 95.

Startup

The first time a NetOp module is run, a dialog will prompt the user to go through a modem setup. After selecting Yes, a dialog will appear.

Connect using

The drop down list should contain all modems that have been setup in Windows. Choose one from the drop-down list. The Communication profile you have created will take the name of the modem you have chosen. If the list is empty no modems have been set up in Windows, or the modem(s) entered are not supported by NetOp . Click on the Add Modem button to have Windows take you through the modem installation wizard.

Configure

The configure button is used to configure settings such as modem speaker volume, maximum baud rate, etc.

These settings should not be changed normally, and all changes should be made carefully. For more information regarding Windows Modem setup please refer to your operating system documentation and online help system.

After you have clicked OK from the Windows Modem Setup dialog box, a communication profile will be created bearing the name of the modem device you have chosen (e.g. Lasat Unique SAFIRE 288)

Editing a Windows Modem Communication Profile

To edit an existing Windows Modem communication profile or to create a new Windows Modem communication profile, choose the Configuration menu, Communication Profiles from the main Guest Control Panel. From the resulting dialog you may Edit an existing profile or create a New profile.

As in the initial Windows Modem Setup screen you may choose a device from the Connect Using drop down list or choose to configure the particular modem or view it's dialing properties. To add a new modem, click on the Add Modem button.

It is possible to create multiple Windows Modem communication profiles each containing a different device that has been set up in Windows.

Note: If you experience trouble using a particular modem make sure that it has been properly setup in Windows, and all drivers have been installed. A good test of this is to try and use the particular modem with either the Phone Dialer, Hyperterminal, or one of the other dial-up networking programs available in windows.


Communication Profiles - Serial

The Serial communication profile is available to users of 16-bit (Windows 3.x) and 32-bit (Windows 2000/NT/95/98) operating systems. However users of Windows 2000, NT,98 and 95 should normally use the Windows Modem communication profile for modem communication, and use the Serial Communication Profile if problems are experienced using Windows Modem or if the particular device being used does not support TAPI.

Use the serial device to communicate using the RS-232C interface – typically with a modem over telephone lines or with a null-modem cable.

On Windows 3.x and 9.x, NetOp accesses the COM port through the driver specified by the COMM.DRV key in the [boot] - section of the SYSTEM.INI file (typically COMM.DRV).

Modem

Check Null Modem if the Guest and Host are directly connected with a cable.

Choose a modem from the Modem name list. If your modem is not in the list choose Hayes compatible (2400 bps or slower) or Hayes compatible fast (9600 or faster), or click New Modem to add a new modem definition (see section 11.8.3 , "The Modem Database").

COM Port

Specify which Com port your modem is connected to (COM1-COM9).

Data Rate

Should normally be Default, which means that NetOp will use the speed defined for the chosen modem in the modem database.

If connection is often lost, try lowering the data rate.

Flow Control

Specifies whether NetOp should use hardware flow control (RTS/CTS). Normally Flow Control should be set to Default. Doing this results in NetOp reading the flow control setting from the modem definition.¨

Dial Type

Choose Tone if this is supported by the phone system. Otherwise choose Pulse.

See also:

The Modem Database

The Modem Dialog


Modem Database

When communicating with a Host via a serial communication profile you typically need to take the specific brand and type of modem into consideration.

NetOp handles this by supplying an open modem database. The database initially contains a number of modems defined by Danware but can be supplemented with your own definitions.

To access NetOp's modem database choose Modem database from the Configuration menu, this activates the dialog box shown in the following figure.

The list shows you the existing records in the database, they are always sorted alphabetically.

Searching

You can search for a record by pressing a key. For example pressing A will move you to the first record starting with the letter 'A' (or 'a').

Inserting

If you activate the New button (or press ALT+N), you will add a new record to the database.  Its contents will be similar to the selected record's (except for the name which will be blank), you will be presented with the edit entry dialog (see the following figure).

Deleting

You delete records by clicking the Delete button (or by pressing ALT+D on your keyboard.

Editing

If you activate the Edit button (or press ALT+E) you will edit the selected record.

See also:

Adding new modems


Modem Database - Adding/Editing

For some modems the string Fixed will be displayed in the lower right corner of the edit dialog. This means that the current modem strings have been defined by Danware and cannot be changed. To alter the settings for a fixed modem string, make a copy of the modem definition and make the desired changes to the copy:

1. Select the modem which is to be changed from the modem list.

2. Activate the New button.

3. Enter a name for the copy of the modem definition.

This modem definition will not be fixed and any desired changes can be made to it. How to Define New

Modems

The most important part of defining a modem for NetOp is the setup strings (SETUP1 and SETUP2). NetOp does not distinguish between these two strings. You can just consider them as two lines for your setup string.

You should use the following general approach when constructing the setup string:

1.Load the modem's factory settings (usually AT&F).

2.Specify that if the DTR signal is lowered the modem should disconnect and return to command mode (usually AT&D2).

3.Specify that the CD signal should track the state of the carrier (usually AT&C1).

4.Specify that the modem should use local echo (usually ATE1).

5.If the modem is capable of RTS/CTS flow control, this should be enabled using the appropriate AT command. Also enable RTS/CTS flow control in the settings section of the modem dialog box.

6.Specify that the DTE/DCE rate should be fixed at the DTE speed.

7.If your modem is equipped with error correction and/or data compression, these should be enabled.

8.Instruct the modem to hangup after loss of carrier (usually by setting the modem's S10 register. E.g. ATS10=20, causing the modem to hangup if carrier is lost for a duration of 2 seconds).

The Dial string should usually be ATD?D. This instructs NetOp to use ATDT if tone dial is chosen by the user and ATDP if pulse dial is chosen.

The Hangup string is usually ATH0S0=0. H0 tells the modem to go on hook, S0=0 tells the modem not to answer incoming calls.

The Send field is sent to the modem after setup1 and setup2 but only by the Guest. Usually this field should be left empty.

The answer field should usually contain the string ATS0=<number of rings>, e.g. ATS0=1, this instructs the modem to answer incoming calls after <number of rings> rings.

Set Max Data Rate to the maximum DTE supported by your modem. Please note that you should be careful with high baud rates on slow computers. You might get better performance by setting the baud rate to 19200 rather than 57600 on a slow PC.

Enable RTS/CTS flow control if this is supported by your modem. You might need to enable the RTS/CTS flow control in your modem with AT command, which should be included in SETUP1 or SETUP2.

Please note that you can override the data rate and flow control defined for the modem in device specific settings for serial.


Modem Dialog

NetOp contains a facility, which lets you monitor all commands sent from the Guest to the modem(s) and the modem's responses.

Each line has the form

COMx << command

indicating that command was sent to the serial port COMx (where x is a number between 1 and 9), or:

COMx >> response

indicating that response was received from the serial port COMx.

Please note that most responses are duplicates of the preceding command, this is because NetOp requires the modem to have local echo enabled, making the modem echo every command back to the PC.


Log Setup

The log setup can be started from the Guest and/or the Host machine, as well as from a Log Server and an Access Server.

To start the log feature select the option Log setup from the Configuration menu.

When you have selected the Log setup, the following dialog will appear.

Log Events

There are two options as to how you can log events from your Guest or Host machine.  Logging events locally or logging events on a NetOp Log Server.

The option Log events locally will create a log file which will be located on your local hard drive.  To select this option activate the Log events locally check box.

The option Log events on a NetOp Log Server will log to a log file located on a NetOp Log Server. To select this option activate the Log events on a NetOp Log Server check box.

If you select this option you must specify a name of the special NetOp Log Server Host. If you know the name of the Host, enter the name in the Host ID for Log Server field or use the Browse button to search for Hosts that are setup as Log Servers.

Log Server

The Log Server module is a special version of the NetOp Host module, which can act as a logging mechanism for NetOp activity. For this special module an extra option to act as Log Server is available in the Log Setup dialog. If this option is enabled then your PC can be used to log events from other NetOp modules.

To activate this option, simply enable the Act as Log Server check box in the Log Server section of the dialog.  If you wish to stop your machine from acting as a Log Server disable the Act as Log Server check box.

Events to Log

After you have selected where and how to log, it is possible to select which events you wish to log.

You will notice that the default setting is for all events to be logged.  This is shown by all of the check boxes being enabled.

To add or remove an event from being logged, select the event and enable or disable the appropriate check box. The changes you make will not take effect until the OK button is pressed.

When these events have been logged, they will appear in abbreviated form in the log file. See the following section "Log File".

Table 12-2.1 and Table 12-2.2  in Chapter 12 ' Appendix'  show how the abbreviated form will appear when logged in the log file.

Log File

Once you have configured your log setup you can send all log activity to a file.  The default name for this file is NETOP.LOG and will be saved in your NetOp directory.

If you wish to change the log file name you can do so by typing the new file name in the Log file name field.

NetOp has the option of immediately flushing each line to disk.  This means that if this option is enabled NetOp bypasses the machine's cache memory thereby keeping the log safer from data loss, for example, if your machine suddenly crashed.

To select this option, enable the Write to disk for each log entry check box in the log file section of the dialog.

See also:

Browsing for Log Servers

Example log file


Log Setup - Browsing for Log Servers

From the Log Server browse dialog a you will be presented with a list of available Log Servers, select the Log Server you wish to log events on. The NetOp Log File will then be placed on the Log Server PC.


Log Setup - Log file example

The following is an example of a short log file. The file comes from a Host called 'John' that is logging locally. The Guest connects and starts a remote control session with the Host, then starts a file transfer.

Each line starts with the date and time the event was logged. The digit after the Host name (john) is the sequence in which the events were logged. The zeros are error message fields and will change if any errors occur. The next field states the event logged. The first line also shows the MAC Address of the Guest. When a file transfer is initiated, the log file lists all files that were sent or received.

19970611,08:44,john,0,00000,00000,START REMO,0x00001700559D

19970611,08:46,john,1,00000,00000,FILERECV,C:\TRANS\NHOST.EXE

19970611,08:46,john,2,00000,00000,FILERECV,C:\TRANS\NHOST.DLL

19970611,08:46,john,3,00000,00000,FILERECV,C:\TRANS\NHOST.CFG

19970611,08:48,john,4,00000,00000,STOP REMO,0x00001700559D

19970611,08:48,john,5,00000,00000,STOP HOST,


Communication Profiles - Gateway

Description

A  "Gateway" Communication profile is used, if a user wishes to route a NetOp remote control call through an Outgoing Gateway. NetOp will route the call through the networking protocol chosen by the user to the Gateway where the call will be routed onwards through one of the dial-up protocols Windows modem, Serial, ISDN, TCP/IP (TCP) or Infrared.

Access Gateway Via Communication Profile.

In this field specify the networking communication profile used to reach the Outgoing Gateway. You may choose from IPX, NetBIOS, TCP/IP (UDP) or <any initialized protocol >.

Gateway Device Group

Use this setting to choose whether NetOp should browse for available device groups on a network, or whether a particular device group should be used.

See also:

Calling through an outgoing Gateway


Communication Profiles - TCP/IP (TCP)

Description

IP is a networking protocol increasingly popular in LAN/WAN environments. It is also the protocol used on the Internet. NetOp supports any 100% WinSock 1.1 compatible implementation.

NetOp has two communication devices based on IP, TCP/IP (UDP) and TCP/IP (TCP). The TCP based version uses TCP ports, and because it is based on point-to-point TCP, you can't browse directly on this device. You can however dial up to, and browse through a Gateway.

Device Specific Settings

.As all packet size issues are handled automatically, there is only one device specific settings in the Communication Profile Edit dialog when using TCP/IP (TCP): Optimize for Internet communication means that NetOp will use 3 MB for the bitmap mode cache and make Automatic compression mean High. Otherwise Automatic compression defaults to low compression on TCP/IP.

Ports

You can assign TCP port numbers to each TCP/IP (TCP) profile like you can for TCP/IP (UDP). However the receive port number is only used for listening. This device will always automatically assigns dynamic numbers when calling.


Communication Profiles - Infrared

Windows 98 and Windows 2000 support communication via infrared light, the method you are familiar with from your TV remote control. Infrared transmission is attractive because you need no cables, and you can get speeds up to 4 megabit per second today, at the release of NetOp 6.5. The limitation is that you can only communicate over a shorter distance.

All settings of the infrared communication is done via Windows' dialogs.  Make sure Windows signals a working communication before trying with NetOp.


Communication Profiles - Editing

Description of Communication Profile

This is the name with which you wish to identify the current communication profile.

Communication Device

Choose the communication device to use for the profile.  This can either be NetBIOS for Microsoft/IBM networks or compatible, IPX for Novell networks or compatible, TCP/IP (UDP)  for IP networks, TCP/IP (TCP)  for IP networks, Windows Modem /Serial for modem or null modem communication or ISDN for communication on the ISDN network with a CAPI compatible adapter or Infrared if you are on Windows 98 or 2000. Consult your system administrator if you are in doubt about which device you should use for communication.

Device specific

In the lower part of the dialog box you will find parameters, which vary with the communication device you have chosen

NetBIOS

   IPX

   TCP/IP (UDP)

   TCP/IP (TCP)

   Windows Modem

Serial

ISDN

   Infrared

Gateway Specific


Program Options - Remote Printing

The NetOp Remote Print facility allows a Guest to redirect a print job to a Host and vice-versa. This option is available for Windows 95/98, Windows NT4 and Windows 2000.

Add Printer

This option will allow you to add a Windows printer, which is used as NetOp printer. A NetOp printer appears to Windows to be a local printer, but the print jobs routed to it are redirected to the other end of your NetOp connection and printed on one of the Windows printers defined there. A NetOp printer uses a port named "NetOp:", where other printers use ports named for example "COM1:" or "LPT1:" The NetOp: port is installed when you install NetOp.

Once you have clicked the Add Printer button, NetOp will launch Windows' Add Printer Wizard and wait for you to press the Ready button when you are done with the Windows Wizard. You can do exactly the same without starting NetOp at all., if you start manually from Printers in the Control panel or from Printers in the Start menu

To add a to add a NetOp Printer please follow these guidelines, which assume you have started Window's Add Printer Wizard in one of the three ways described earlier. This Wizard is slightly different on different Windows versions, so on your computer the items below may not appear exactly as listed.

1. Configure the printer to be a local printer. This is sometimes stated as managed by My Computer. Windows must believe that this is a local printer, and must not be aware that NetOp takes the print jobs and redirects them. If there is a checkbox referring to plug and play, make sure you uncheck that box.

2. In the Available Ports dialog select the port named "NetOp:" (On 95/98 this is item 3, not 2).

3. Select the printer manufacturer and model, which matches the printer you want to print on. That printer is not physically attached to the computer you are running the Add Printer Wizard on, but to the computer in the other end of the NetOp connection. (On 95/98 this is item 2, not 3).

4. Give the printer a name you can easily recognize. One idea is to append "Netop" to the automatically generated name. You can choose whether it makes sense for you to have this printer as your default printer, as it only works when there is a NetOp connection active. Otherwise, printing on it will produce a "Printer not ready" message.

5. The printer may not be shared.

6. If you select to print a test page, make sure a NetOp connection is active.

7. Click on the Finish button.

When a print job is sent to the NetOp Printer on the one end of a NetOp connection, it will be redirected to the other end, where it will be printed physically.

Print the document on the default printer

By selecting this option, any print job redirected through a NetOp printer to a Host will automatically be printed on the Host's default printer.

Prompt with a list of available Printers

By selecting this option, the Guest will prompt its user with a list of available printers on the Host, whenever a print job is redirected. The user at the Guest can then select the printer that should be used for the particular job.